New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: WalletConnect/WalletConnectSharp#79 #141

Merged

skibitsky merged 3 commits into 2.0 from fix/broken-connection-after-1m

Oct 20, 2023

+22 −22

Member

skibitsky commented Oct 17, 2023 •

edited

Loading

The behaviour was caused by two issues:

WebSocket connection experiencing a timeout after 60 seconds of inactivity due to the default behavior of the WebSocket.Client library (reconnection docs).
WebSocket connection disconnected by WalletConnect Relay's load balancer after 5 minutes of inactivity. After the Relayer reconnects, some of its events didn't reach the Subscriber, resulting in topics not being resubscribed.

This PR fixes #79


          fix: #79

2a12dd7

skibitsky mentioned this pull request

Throwing exceptions when after few minutes with no interaction #79

Closed

skibitsky added 2 commits

October 19, 2023 15:27


          fix: Subscriber not receiving events from Relayer after reconnect

a3a7ce3


          chore: rename some fields in Subscriber to match conventions

bba4e4e

skibitsky merged commit 0eb2ee5 into 2.0

2 checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet